Validate valid value rule area (container)

Rule Name:

Replace any tabs in valid value rule with 3 spaces

Position:

Under: Validate valid value rule area

Name:

VVR_RemoveTabs

Default:

Checked

Usage:

The valid value rule field is parsed and any occurrences of tab characters are replaced with three spaces. Spaces are preferred over tabs so that when printed in a mono-spaced type the listing appears correct.  If changes were made, a note is added to the log and displayed. 

Rule Name:

Replace any non-ASCII chars (values >127) with pure ASCII

Position:

Under: Validate valid value rule area

Name:

VVR_JustASCII

Default:

Checked

Usage:

The valid value rule field is parsed and any occurrences of characters with hex values above 127 are replaced. The replacement strings are taken from similar characters when possible (for example, the right hanging quote symbol is replaced with a straight quote).  If changes were made, a note is added to the log and displayed. 

Rule Name:

Indent trailing lines of code by 3 spaces (pretty print)

Position:

Under: Validate valid value rule area

Name:

VVR_IndentLines

Default:

Checked

Usage:

The valid value rule field is parsed and all lines following after the first line are indented at least three spaces to present some white space along the left edge of the listing.  A rather primitive pretty print.  If changes were made, a note is added to the log and displayed. 

Rule Name:

Make text entries into valid comments

Position:

Under: Validate valid value rule area

Name:

Make_Comments

Default:

Checked

Usage:

The valid value rule field is parsed and any content found after the “code” part which seems to be a possible comment is rendered into a legal ASN comment (typically by preceding it with  two dashes).  Many early standards did not insert proper comment marks in their work, and this rule was developed to correct this.  If changes were made, a note is added to the log and displayed.

Rule Name:

Correct INTEGER range limits

Position:

Under: Validate valid value rule area

Name:

Scrub_INTEGERS

Default:

Checked

Usage:

The overall ASN is parsed and if it is determined to be an INTEGER type,  the valid value rule “code” part is examined to detect any possible valid range limits. 

Any ranges that are found are re-stated in a syntactically valid and correct way.  Properly formed ASN is left unchanged  Many early standards did not handle limit ranges correctly, and this rule was developed to correct this.  If changes were made, a note is added to the log and displayed.

Rule Name:

Correct IA5STRING size limits

Position:

Under: Validate valid value rule area

Name:

Scrub_STRINGS

Default:

Checked

Usage:

The overall ASN is parsed and if it is determined to be an IA5String type,  the valid value rule “code” part is examined to detect any possible valid range limits for the string. 

Any ranges that are found are re-stated in a syntactically valid and correct way.  Properly formed ASN is left unchanged  Many early standards did not handle limit ranges correctly, and this rule was developed to correct this.  If changes were made, a note is added to the log and displayed.

Rule Name:

Correct ENUMERATION lists

Position:

Under: Validate valid value rule area

Name:

Scrub_ENUMS

Default:

Checked

Usage:

The overall ASN is parsed and if it is determined to be an ENUMERATED type,  the valid value rule “code” part is examined to extract any possible strings and values. 

Any “sets” of data that are found are placed into an array, sorted, and re-stated in a syntactically valid and correct way, including any comment for that line.  Properly formed ASN is left unchanged  Many early standards did not handle enumerated lists of items correctly, and this rule was developed to correct this.  If changes were made, a note is added to the log and displayed.

Rule Name:

Correct BIT STRING lists

Position:

Under: Validate valid value rule area

Name:

Scrub_BITSTRINGS

Default:

Checked

Usage:

The overall ASN is parsed and if it is determined to be an BIT STRING type,  the valid value rule “code” part is examined to extract any possible strings and values. 

Any “sets” of data that are found are placed into an array, sorted, and re-stated in a syntactically valid and correct way, including any comment for that line.  Properly formed ASN is left unchanged  Many early standards did not handle enumerated lists of items correctly, and this rule was developed to correct this.  If changes were made, a note is added to the log and displayed.

Rule Name:

Replace occurrences of 3-dot char with "..."   

Position:

Under: Validate valid value rule area

Name:

ASN_3_Dots

Default:

Checked

Usage:

Those creating the standards using MS Word often have a problem with its autocorrect feature mucking up source code listings.  One of the ways in which this occurs is that three periods in a row are translated to an (illegal in ASN) symbol.  This rule detects this symbol and replace it with the three periods needed by valid ASN.  If changes were made, a note is added to the log and displayed.

Aside: This, and several other annoying autocorrect changes, can be changed in MS Word as follows.  In Word 2000, under Tools, in the Autocorrect command, in the AutoCorrect tab: There you will see a list box with "…" listed in it, delete this entry. Further down in this section you can also find the "itis" to "it is" rule which may also be annoying you by this time.

Rule Name:

Replace occurrences of 4294967296 with 4294967295 (max unsigned value)

Position:

Under: Validate valid value rule area

Name:

ASN_BigValues1

Default:

UN-Checked

Usage:

The valid value rule is parsed and if it is an INTEGER data type, and the upper range is set to 4294967296, then it is changed to be 4294967295 (which is the max allowed value in a 32 bit unsigned variable, recall that the range is defined as 0 to 2^{^N} –1).  If changes were made, a note is added to the log and displayed.

Rule Name:

Replace occurrences of 2147483648 with 2147483647 (max signed value)

Position:

Under: Validate valid value rule area

Name:

ASN_BigValues2

Default:

UN-Checked

Usage:

The valid value rule is parsed and if it is an INTEGER data type, and the upper range is set to 2147483648, then it is changed to be 2147483647 (which is the max allowed value in a 32 bit signed variable, recall that the range is defined as 0 to 2^{^N} –1).  If changes were made, a note is added to the log and displayed.